<link linkend="filter_polygon">polygon</link> filters. See those filters
for more information.
</para>
+<para>
+The arc format reads two numeric fields, a latitude and a longitude,
+in any format recognized as <link linkend="style_def_lathuman">human
+readable</link> and writes as simple degrees decimal. It really is
+intended for GPSBabel's own internal use more than general use, though
+it turns out to be a convenient way of expressing simple polylines and
+polygons.
+</para>
- <para>This is the format used by CoastalExplorer (tm). The
+ <para>This is the format used by <productname>CoastalExplorer</productname>. The
format is XML with items uniquely identified by Windows-style UUIDs.
<ulink url="http://www.rosepointnav.com">http://www.rosepointnav.com</ulink>
</para>
<para> With this format we can read <ulink url="http://phgiraud.free.fr/CarteSurTable/CarteSurTable.htm">CarteSurTable</ulink>data files.
- <ulink url="http://phgiraud.free.fr/CarteSurTable/CarteSurTable.htm">CarteSurTable</ulink>is a shareware program widely used in France. The data
+ <ulink url="http://phgiraud.free.fr/CarteSurTable/CarteSurTable.htm">CarteSurTable</ulink> is a shareware program widely used in France. The data
inside have to be seen as a mixture of a waypoints list, one route and
several tracks.
</para>
<para> There are a billion variants of Comma Separated Value
-data. This is the one that makes <ulink url="http://www.delorme.com">Delorme
"</ulink> <productname>S&A Deluxe 9</productname> happy. It's
+data. This is the one that makes <ulink url="http://www.delorme.com">Delorme</ulink> <productname>S&A Deluxe 9</productname> happy. It's
also a very simple program and useful for many other programs like
spreadsheets.</para>
<para> CSV is also the correct format for
their commercial mapping program, or GDM6 (their free waypoint
manager) for iFinder which is available at <ulink url="http://www.lowrance.com/Software/GDM6/Default.asp">lowrance.com</ulink>
</para>
-
+ <para>
+ On write, this format writes simple "latitude, longitude" pairs, but
+on read it will read anything supported by our <link linkend="style_def_lathuman">human readable</link> definition.
+ </para>
+ <para>
+ For something-separated data that has headers identifying the various
+ fields, see our <link linkend="fmt_unicsv">universal csv</link> format.
+ </para>
- <para> This was a requested CSV format, *not* the proprietary
+ <para> This was a requested <link linkend="fmt_csv">CSV format</link>, and is <emphasis>not</emphasis> the proprietary
binary format used by <ulink url="http://www.fugawi.com">Fugawi</ulink>. Like any other CSV format, GPSBabel
cannot read tracks in this format, but converting a track into it and
then importing as track in Fugawi works.</para>
<para>This is format for the
<ulink url="http://vip.hyperusa.com/~dougs/geocachingdb/geocachingdb.htm">
-GeocachingDB</ulink>program by DougsBrat. It works with v2
+GeocachingDB</ulink> program by DougsBrat. It works with v2
and v3 of this program.
</para>
<para>
Support for the "Garmin GPS Database" format used by
-default in MapSource versions since release 6.0. By default GPSBabel creates
+default in <productname>MapSource</productname> versions since release 6.0 of
+that product. By default GPSBabel creates
gdb files of version 2. Version 2 is used in Mapsource 6.3 and 6.5.
</para>
<para>
<para>
-This format supports the Geocaching.com/EasyGPS ".loc" format. This format
+This format supports the <ulink url="http://www.geocaching.com">Geocaching.com</ulink>/<ulink url="http://www.easygps.com">EasyGPS</ulink> ".loc" format. This format
was created specifically for Geocaching.com and is not the same as the
standard EasyGPS .loc format. See the <link linkend="fmt_easygps">EasyGPS</link>
or <link linkend="fmt_gpx">GPX</link> formats for more general EasyGPS support.
<para>This is the XML format used by the Garmin Logbook product
-that ships with Forerunner and Foretrex. <ulink url="http://www.garmin.com">http://www.garmin.com</ulink>
+that ships with Forerunner and Foretrex.
+As of early 2006, this program is apparently been discontinued in favor of
+<link linkend="fmt_gtrnctr">Garmin Training Center</link>.
+
+See: <ulink url="http://www.garmin.com">http://www.garmin.com</ulink>
</para>
<para> This format is designed to read the XML emitted when you
-tack "&output=js" onto the end of a Google Maps route URL (use
+tack "&output=js" onto the end of a <ulink url="http://www.maps.google.com>Google Maps">Google Maps</ulink>route URL (use
the "link to this page" option to get a usable URL.) This allows you
to plan a route using Google Maps, then download it and use it in your
own mapping program or GPS receiver. To get a file suitable for use
- <para> This is a Palm/OS file format for GPilotS. It was tested
-against version 6.2.
+ <para> This is a Palm/OS file format for
+ <ulink url="http://www.cru.fr/perso/cc/GPilotS/">GPilotS</ulink>.
+ It was tested against version 6.2 of GPilotsS
</para>
- <para>
- <ulink url="http://www.cru.fr/perso/cc/GPilotS/">http://www.cru.fr/perso/cc/GPilotS/</ulink>
- </para>
<para> Neither tracks nor routes are supported at this
time.</para>
- <para>GPSUtil has a simple file format of this program that runs
+ <para>The format we call <ulink url="http://www.cs.uakron.edu/~hennings/gpsutil">gpsutil</ulink> is a simple file format used by a program that runs
on POSIX- compliant OSes like UNIX and Linux. Reads and writes of
-this format are reliable. (I've also contributed to this program.)
-It's available at <ulink url="http://www.cs.uakron.edu/~hennings/gpsutil">cs.uakron.edu</ulink>.</para>
+this format are very reliable. (<ulink url="/people/robertlipe.html">The lead
+developer of GPSBabel</ulink> also contributed to this that 'gpsutil'
+the early days.)</para>
+<para>
+ Note that 'gpsutil' is a different format - and program - than the one called <ulink url="http://www.gpsu.co.uk/index.html">GPS Utility</ulink>; for that one, you should probably use our <link linkend="fmt_pcx">PCX module</link>.
+</para>
supported by EasyGPS, ExpertGPS, and many other programs described at
<ulink url="http://www.topografix.com/gpx_resources.asp">topografix.com</ulink>
</para>
+ <para>
+ GPSBabel's reader of this module attempts to preserve tags it doesn't
+ really understand. It also tries to glean interesting data from
+ <ulink url="http://www.geocaching.com">pocket queries from Geocaching.com</ulink>.
+ </para>
- <para> The Holuxgm-100 (e-fox) gps receiver uses standard
+ <para> The Holux gm-100 (e-fox) gps receiver uses standard
compact flash cards. File formats were provided by Holux-Taiwan
<ulink url="http://www.holux.com.tw">holux.com</ulink> to the author.
The code was tested against version 2.27E1; other versions and
<para>
KML, the Keyhole Markup Language, is used by Keyhole and
-Google Earth. There are features in this file format that GPSBabel
+<ulink url="http://earth.google.com">Google Earth</ulink>. There are features in this file format that GPSBabel
doesn't support - such as camera views - but waypoints, tracks, and routes
work well.
</para>
<para>
-The Lowrance iFinder GPS series has the unique capability
+The <ulink url="http://www.lowrance.com">Lowrance iFinder GPS</ulink> series has the unique capability
to output its data to an MMC card. The data is saved to the card as a
.USR file and can be read by your computer using a card reader.
Waypoints, routes, tracks are supported. By default, Event marker
-<para>GPSBabel supports the following Magellan receivers:
+<para>GPSBabel supports the following <ulink url="http://www.magellangps.com">Magellan</ulink> receivers:
<simplelist columns="2">
<member>310</member>
<member>315</member>
-<para>GPSBabel supports the following Magellan receivers:
+<para>GPSBabel supports the following <ulink url="http://www.magellangps.com">Magellan</ulink> receivers:
<simplelist columns="2">
<member>310</member>
<member>315</member>
<para>
- This is the SD card format used by the Magellan Explorist 400,
+ This is the SD card format used by the <ulink url="http://www.magellangps.com">Magellan</ulink> Explorist 400,
500, 600, and XL and internally on those devices plus the
- Explorist 210. Waypoints are identical to the Magellan SD format
- used by Meridian, but allows longer waypoint names. Routes are
+ Explorist 210. Storeed waypoints are identical to the Magellan SD format
+ used by Meridian, but the newer models allow longer waypoint names. Routes are
subtly different.
</para>
<para>
- <para> The SD card format used by the Magellan Explorist 400,
-500, and 600 to describe geocaches. Notice what while the format can
+ <para> The SD card format used by the <ulink url="http://www.magellangps.com">Magellan</ulink> > 400,
+500, 600, 210, and XL to describe geocaches. Notice what while the format can
hold an infinite number of geocaches, the unit will read and silently
discard all but 200 geocache POIs at a time.</para>
<para> You should name any file created with this format with a
<para>
-Magellan NAV Companion for Palm/OS is not really designed
+<ulink url="http://www.magellangs.com">Magellan</ulink> NAV Companion for Palm/OS is not really designed
for this sort of use, but its file format is supported and with a
little bit of patience you can both read and write NAV Companion
waypoints. This conversion is based on
<para>
-This format supports the
Magellan <productname>MapSend</productname> native
+This format supports the
<ulink url="http://www.magellangps.com">Magellan</ulink> <productname>MapSend</productname> native
file format.
</para>
<para>
<ulink url="http://www.sparkfun.com/commerce/product_info.php?products_id=671">SparkFun GPS Datalogger</ulink>
</member>
</simplelist>
+<para>
+This module also supports <link linkend="tracking">realtime tracking</link>
+which allows realtime position reports from a GPS, such as one connected
+serially, over Bluetooth, or a USB module emulating a serial port, to be used
+with selected output formats.
+</para>
<para>The option 'datum="datum name"' can be used to override
the default of NAD27 ("N. America 1927 mean") which is correct for the
-continental U.S. Points in Hawaii should use "Old
-Hawaiian_mean"</para>
+continental U.S.</para> <para>Any legal <link linkend="Datums">datum supported
+by GPSBabel</link> may be used. For example, points in Hawaii should
+use "Old Hawaiian_mean".</para>
the lame NMEA six-character waypoint names that's treated as a
second-class citizien in current versions of MapSource. In Mapsource,
use file->import to read these files. If you name the files *.wpt,
-Mapsource will find them easier.
+Mapsource will find them more easily.
</para>
<para> In general, you should prefer the "mapsource" file format
to this one.
</para>
-
+ <para>This format has been extended to handle many - but not all -
+ files from <ulink url="http://www.gpsu.co.uk/index.html">GPS Utility</ulink>. If you encounter something that GPSBabel does not handle well, use
+the free version of GPSUtil to read it and save as something more common.
+ </para>
- <para> This is a format for importing into Microsoft Streets and
-Trips. It's been exercised on versions 2003, 2004, and 2005. Detailed
+ <para> This is a format for importing into
+<ulink url="http://www.microsoft.com/streets/default.mspx"> Microsoft Streets and
+Trips</ulink>. It's been exercised on versions from 2003 through 2007. Detailed
instructions on how to use it, including preserving hyperlinks, are at
<ulink url="http://www.gpsbabel.org/formats/s_and_t/Importing_into_Microsoft_Streets_and_Trips_2003.html">gpsbabel.org</ulink>
</para>
- <para> This format is for Street Atlas USA 2004 Plus.
+ <para> This format is for Delorme Street Atlas USA 2004 Plus and later.
</para>
<para> For geocachers importing data from a tool like GSAK or
Spinner, import the file twice in XData. One will create a file with
- <para>TopoMapPro Places File. Reads and writes places files for
-use in TopoMapPro <ulink url="http://www.topomappro.com">topomappro.com</ulink>). As this file
+ <para>Reads and writes places files for
+use in <ulink url="http://www.topomappro.com">TopoMapPro places files</ulink>). As this file
type can store links other than web links, anything that is not a http
url will be discarded. Note that this does not do datum conversions,
so if your input file does not have WGS84/NZGD2000 data, your output
- <para> This format can read and write TomTom .ov2 (POI) files,
+ <para> This format can read and write <ulink url="http://www.tomtom.com">TomTom</ulink> .ov2 (POI) files,
as used by the TomTom GO and TomTom Navigator. It has been tested
with an original TomTom GO running version 5.00 of the TomTom
software. There may be some records that confuse the input module -
- <para>Delorme TopoUSA/XMap Conduit is one of the billion CSV
-variants mentioned above. It's just like S&A with the addition of
+ <para>Delorme TopoUSA/XMap Conduit is one of the bazillion
+<link linkend="fmt_csv">CSV variants</link>
+variants mentioned above. It's just like Delorme Streets & Atlas with the addition of
a completely pointless line at the beginning and end of the file. This
is the format used to hot-sync to XMap from withing TopoUSA. Done with
help of Dan Edwards.</para>
- <para>Delorme XMap2006 Conduit is just like XMap, except there are
+ <para>Delorme XMap2006 Conduit is just like
+<link linkend="fmt_xmap">XMap</link>
+, except there are
no spaces between fields and the coordinate format is slightly
different. The completely pointless header and footer lines
are the same, at least. Use this to create the XMapHHWptsSend.txt
<para>
Delorme XMapHandHeld Street Atlas USA is another of the
-billion CSV variants. This is the format used by XmapHH SA USA on (at
-least) PocketPC O/S.
+billion <link linkend="fmt_csv"> CSV variants</link>.
+This is the format used by XmapHH SA USA on (at least) PocketPC O/S.
</para>
<para>
This XMap is not the same as the simpler
projects / gpsbabel.git / commitdiff